Intermediary server, remote control system, and mediating method

ABSTRACT

An intermediary server includes circuitry to receive, from a reservation management server, resource identification information for identifying a resource. The reservation management server manages a reservation for the resource and receives the reservation from a registration terminal that registers the reservation. The circuitry further transmits, to a drive control server, drive device identification information for identifying a drive device corresponding to the resource identification information. The drive control server remotely controls the drive device used to unlock the resource. The circuitry further receives, from the drive control server, authentication information to be used to unlock the resource with the drive device identified by the drive device identification information. The circuitry further receives, transmit, to the registration terminal, the authentication information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is based on and claims priority pursuant to 35U.S.C. § 119(a) to Japanese Patent Application No. 2020-104742, filed onJun. 17, 2020, in the Japan Patent Office, the entire disclosure ofwhich is hereby incorporated by reference.

BACKGROUND Technical Field

The present disclosure relates to an intermediary server, a remotecontrol system, and a mediating method.

Related Art

In recent years, a system for remotely unlocking (or locking) a resourcewith a smart lock by remotely controlling the smart lock from asmartphone via a server has been provided. Such a smart lock allows auser to unlock or lock a door of a shared resource, such as a meetingroom in an office or a vehicle used for a car sharing service, inaddition to a door of a privately owned resource, such as a door of ahouse or an apartment.

SUMMARY

An exemplary embodiment of the present disclosure includes anintermediary server including circuitry to receive, from a reservationmanagement server, resource identification information for identifying aresource. The reservation management server manages a reservation forthe resource and receives the reservation from a registration terminalthat registers the reservation. The circuitry further transmits, to adrive control server, drive device identification information foridentifying a drive device corresponding to the resource identificationinformation. The drive control server remotely controls the drive deviceused to unlock the resource. The circuitry further receives, from thedrive control server, authentication information to be used to unlockthe resource with the drive device identified by the drive deviceidentification information. The circuitry further receives, transmit, tothe registration terminal, the authentication information.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the disclosure and many of the attendantadvantages and features thereof can be readily obtained and understoodfrom the following detailed description with reference to theaccompanying drawings, wherein:

FIG. 1 is a schematic view of a remote control system according to oneor more embodiments of the disclosure;

FIG. 2 is a block diagram illustrating a hardware configuration of apersonal computer (PC), a reservation management server, an intermediaryserver, or a drive control server according to one or more embodimentsof the disclosure;

FIG. 3 is a block diagram illustrating a hardware configuration of asmartphone according to one or more embodiments of the disclosure;

FIG. 4 is a block diagram illustrating a hardware configuration of asmart lock according to one or more embodiments of the disclosure;

FIG. 5 is a block diagram illustrating a functional configuration ofdevices included in a remote control system according to one or moreembodiments of the disclosure;

FIG. 6 is a conceptual diagram illustrating a reservation managementtable according to one or more embodiments of the disclosure;

FIG. 7A is a conceptual diagram illustrating a user management tableaccording to one or more embodiments of the disclosure;

FIG. 7B is a conceptual diagram illustrating an event management tableaccording to one or more embodiments of the disclosure;

FIG. 7C is a conceptual diagram illustrating a key type management tableaccording to one or more embodiments of the disclosure;

FIG. 8 is a conceptual diagram illustrating a drive device managementtable according to one or more embodiments of the disclosure;

FIG. 9 is a sequence diagram illustrating a reservation registrationprocess according to one or more embodiments of the disclosure;

FIG. 10 is a diagram illustrating an example of a schedule input screenaccording to one or more embodiments of the disclosure;

FIG. 11 is a sequence diagram illustrating a process performed in a casethat a user is not authenticated as an authorized user, according to oneor more embodiments of the disclosure;

FIG. 12 is a flowchart illustrating a key type determination processperformed by an intermediary server when a user is authenticatedsuccessfully, according to one or more embodiments of the disclosure;

FIG. 13 is a sequence diagram illustrating a process of transmitting amessage when a key type is indicated as “ELECTRONIC KEY”, according toone or more embodiments of the disclosure;

FIG. 14 is an illustration of an example screen displayed on a PC when akey type is indicated as “ELECTRONIC KEY” according to one or moreembodiments of the disclosure;

FIG. 15 is a sequence diagram illustrating a process of transmitting amessage when a key type is indicated as “PHYSICAL KEY”, according to oneor more embodiments of the disclosure;

FIG. 16 is an illustration of an example screen displayed on a PC whenthe key type is indicated as “PHYSICAL KEY”, according to one or moreembodiments of the disclosure;

FIG. 17 is a sequence diagram illustrating a process of transmitting amessage when a key type is indicated as “NONE”, according to one or moreembodiments of the disclosure;

FIG. 18 is an illustration of an example screen displayed on a PC when akey type is indicated as “NONE”, according to one or more embodiments ofthe disclosure;

FIG. 19 is a sequence diagram illustrating a remote unlocking processwhen a key type is indicated as “ELECTRONIC KEY”, according to one ormore embodiments of the disclosure;

FIG. 20 is another sequence diagram illustrating a remote unlockingprocess when a key type is indicated as “ELECTRONIC KEY”, according toone or more embodiments of the disclosure;

FIG. 21 is still another sequence diagram illustrating a remoteunlocking process when a key type is indicated as “ELECTRONIC KEY”,according to one or more embodiments of the disclosure;

FIG. 22A to FIG. 22D are illustrations of example screens displayed on asmartphone when a conference starts, according to one or moreembodiments of the disclosure;

FIG. 23 is a sequence diagram illustrating a remote locking process whena key type is indicated as “ELECTRONIC KEY”, according to one or moreembodiments of the disclosure; and

FIG. 24 is another sequence diagram illustrating a remote lockingprocess when a key type is indicated as “ELECTRONIC KEY”, according toone or more embodiments of the disclosure.

The accompanying drawings are intended to depict embodiments of thepresent invention and should not be interpreted to limit the scopethereof. The accompanying drawings are not to be considered as drawn toscale unless explicitly noted. Also, identical or similar referencenumerals designate identical or similar components throughout theseveral views.

DETAILED DESCRIPTION

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinvention. As used herein, the singular forms “a,” “an,” and “the” areintended to include the plural fauns as well, unless the context clearlyindicates otherwise.

In describing embodiments illustrated in the drawings, specificterminology is employed for the sake of clarity. However, the disclosureof this specification is not intended to be limited to the specificterminology so selected and it is to be understood that each specificelement includes all technical equivalents that have a similar function,operate in a similar manner, and achieve a similar result.

Embodiments of the present disclosure are described in detail below,with reference to the drawings.

Overview of System:

A description is given below of an overview of a remote control system 1according to an exemplary embodiment. FIG. 1 is a schematic view of theremote control system 1 according to the present embodiment. In thedescription of the present embodiment, a case where a smartphone 3remotely unlocks or locks a smart lock 9 set outside a door 8 of aresource such as Conference Room (Meeting Room) A (outside ConferenceRoom A) is described.

As illustrated in FIG. 1, the remote control system 1 includes apersonal computer (PC) 2, the smartphone 3, a reservation managementserver 5, an intermediary server 6, a drive control server 7, and thesmart lock 9. The above-described elements communicate each other via acommunication network 100 such as the Internet. The communicationnetwork 100 may include not only a wired communication network but alsoa wireless communication network such as a mobile communication system(4G, 5G, 6G, etc.) and Worldwide Interoperability for Microwave Access(WiMAX).

The PC 2, the smartphone 3, and the smart lock 9 are owned by the samebusiness operator (organization) such as a company. Hereinafter, as anexample of the organization, a company is used in the description of theembodiment. There are Conference Room A, Conference Room B, andConference Room C in a building of the company. In FIG. 1, ConferenceRoom A is illustrated. A sticker on which QR CODE is printed is affixedto an outer surface of the door 8 of Conference Room A (the outside ofconference room A). QR CODE printed on the sticker is embedded withresource identification information (ID) (for example, resource ID) foridentifying Conference Room A and access destination information (accesslocation information, access/location information).

The PC 2 is, for example, a laptop PC used by User A, and is an exampleof a registration terminal used by User A to register his or herschedules or reservations for resources (resource reservations) in thereservation management server 5.

The smartphone 3 is an example of a (mobile) communication terminalcarried by User A.

The smart lock 9 is installed in a key portion of the door 8 and has amechanism capable of unlocking and locking the door 8. Further, QR CODE(registered trademark) 10 such as a barcode is indicated on or near bythe door 8. QR CODE 10 is printed on the sticker to be sticked on thedoor 8. QR CODE 10 is embedded with the resource ID for identifying aresource, such as a conference room for which the door 8 is installed,and the access destination information (for example, Uniform ResourceLocator (URL)) in relation to the intermediary server 6. The stickerindicating QR CODE 10 is attached to a part of the resource such as thedoor 8 to associate QR CODE 10 and the resource. The smartphone 3installed with an application of a QR CODE scanner acquires QR CODEinformation by the QR CODE scanner.

The smart lock 9 is an example of a drive device provided by the companythat operates the drive control server 7 to an organization (company) towhich User A belongs. In a case of a smart lock for a door, the smartlock 9 is attached to a thumb turn of the door 8, and the smart lock 9rotates the thumb turn by being remotely operated to unlock or lock thedoor 8.

The reservation management server 5, the intermediary server 6, and thedrive control server 7 are individually managed by different companies.The reservation management server 5 is, for example, a server ofMICROSOFT (registered trademark) 365. The intermediary server 6 is, forexample a server managed by a service provider that provides a servicein which a reservation management service, such as MICROSOFT (registeredtrademark) 365, and a remote unlocking (or locking) service of the smartlock 9 are associated and cooperated with each other. The drive controlserver 7 is a server provided by the company that sells the smart lock 9and provides the remote unlocking (or locking) service.

The company that manages the reservation management server 5 and thecompany that manages the drive control server 7 are different from eachother, so that the intermediary server 6 mediates the processing betweenthe reservation management server 5 and the drive control server 7.

Hardware Configuration:

A description is given below of an example of a hardware configurationof each device included in the remote control system 1 with reference toFIG. 2 to FIG. 4.

Hardware configurations of PC or Each Server:

FIG. 2 is a block diagram illustrating a hardware configuration of a PC,a reservation management server, an intermediary server, or a drivecontrol server according to the present embodiment. The hardwareconfiguration of the PC 2 is indicated by a 200 number. Each hardwareconfiguration of the reservation management server 5, the intermediaryserver 6, or the drive control server 7 is the same as that of the PC 2.The hardware configurations of the reservation management server 5, theintermediary server 6, and the drive control server 7 are indicated by a500 number, a 600 number, and a 700 number, respectively.

The PC 2 is implemented by a computer, and includes as illustrated inFIG. 2, a central processing unit (CPU) 201, a read only memory (ROM)202, a random access memory (RAM) 203, a hard disk (HD) 204, a hard diskdrive (HDD) controller 205, a display 208, a network interface (I/F)209, a data bus 210, a keyboard 211, a mouse (pointing device) 212, amedia I/F 207, and a Digital Versatile Disk Rewritable (DVD-RW) drive214.

The CPU 201 controls entire operation of the PC 2. The ROM 202 stores aprogram such as an initial program loader (IPL) used for driving the CPU201. The RAM 203 is used as a work area for the CPU 201. The HD 204stores various data such as a control program. The HDD controller 205reads or writes various data from or to the HD 204 under control of theCPU 201. The display 208 displays various types of information such as acursor, a menu, a window, characters, or an image. The network I/F 209is an interface for data communication by using the communicationnetwork 100. The data bus 210 is an address bus or a data bus thatelectrically connects the elements illustrated in FIG. 2, such as theCPU 201, to each other.

The keyboard 211 is an example of an input device provided with aplurality of keys for allowing a user to input characters, numerals, orvarious instructions. The mouse 212 is one example of input device forselecting or executing various kinds of instructions, selecting anobject to be processed, or for moving a cursor. The media I/F 207 readsor writes (stores) data from or to a recording medium 206 such as aflash memory or the like. The DVD-RW drive 214 reads or writes variousdata from or to a DVD-RW 213, which is an example of a removable storagemedium. The removable storage medium is not limited to the DVD-RW andmay be a digital versatile disc-recordable (DVD-R) or Blu-ray Disc.

Hardware Configuration of Smartphone:

FIG. 3 is a block diagram illustrating a hardware configuration of asmartphone according to the present embodiment. As illustrated in FIG.3, the smartphone 3 includes a CPU 301, a ROM 302, a RAM 303, anelectrically erasable PROM (EEPROM) 304, a Complementary Metal OxideSemiconductor (CMOS) sensor 305, an imaging element I/F 306, anacceleration and orientation sensor 307, a media I/F 309, and a globalpositioning system (GPS) receiver 311.

The CPU 301 controls entire operation of the smartphone 3. The ROM 302stores a program such as an IPL used for driving the CPU 301. The RAM303 is used as a work area for the CPU 301. The EEPROM 304 reads orwrites various data such as a control program for a smartphone undercontrol of the CPU 301. The CMOS sensor 305 is an example of a built-inimaging device that captures an object (mainly, a self-image of a useroperating the smartphone 3) under control of the CPU 301 to obtain imagedata. In alternative to the CMOS sensor, an imaging element such as acharge-coupled device (CCD) sensor may be used. The imaging element I/F306 is a circuit that drives the CMOS sensor 305. The acceleration andorientation sensor 307 includes various sensors such as anelectromagnetic compass or gyrocompass for detecting geomagnetism and anacceleration sensor. The media I/F 309 reads or writes (stores) datafrom or to a recording medium 308 such as a flash memory or the like.The GPS receiver 311 receives a GPS signal from a GPS satellite.

The smartphone 3 further includes a long-range communication circuit312, an antenna 312 a for the long-range communication circuit 312, aCMOS sensor 313, an imaging element I/F 314, a microphone 315, a speaker316, an audio input/output (I/O) I/F 317, a display 318, an externaldevice connection I/F 319, a short-range communication circuit 320, anantenna 320 a for the short-range communication circuit 320, and a touchpanel 321.

The long-range communication circuit 312 is a circuit that enables thesmartphone 3 to communicate with other devices through the communicationnetwork 100. The CMOS sensor 313 is an example of a built-in imagingdevice capable of capturing a subject under control of the CPU 301. Theimaging element I/F 314 is a circuit that drives the CMOS sensor 313.The microphone 315 is a built-in circuit that converts sound into anelectric signal. The speaker 316 is a built-in circuit that generatesaudio such as music or voice by converting an electric signal intophysical vibration. The audio I/O I/F 317 is a circuit for controllinginput and output of audio signals between the microphone 315 and thespeaker 316 under control of the CPU 301. The display 318 is an exampleof a display device that displays an image of the object, various icons,etc. Examples of the display 318 include a Liquid Crystal Display (LCD)and an organic Electro Luminescence (EL) display. The external deviceconnection I/F 319 is an interface for connecting to various externaldevices. The short-range communication circuit 320 is a communicationcircuit that communicates in compliance with the Near FieldCommunication (NFC), the Bluetooth, or the like. The touch panel 321 isan example of an input device that allows a user to operate thesmartphone 3 by touching a screen of the display 318.

The smartphone 3 further includes a bus line 310. The bus line 310 is anaddress bus or a data bus, which electrically connects the hardwareresources illustrated in FIG. 3 such as the CPU 301.

Hardware Configuration of Smart Lock:

FIG. 4 is a block diagram illustrating a hardware configuration of asmart lock according to the present embodiment. The smart lock 9 isprovided with a computer. As illustrated in FIG. 4, the smart lock 9includes a CPU 901, a ROM 902, a RAM 903, a non-volatile random accessmemory (NVRAM) 904, an unlocking/locking device 905, an operation device907, a long-range communication circuit 909, an antenna 909 a for thelong-range communication circuit 909, and a bus line 910.

The CPU 901 controls entire operation of the smart lock 9. The ROM 902stores a program such as an IPL used for driving the CPU 901. The RAM903 is used as a work area for the CPU 901. The NVRAM 904 is anon-volatile memory that stores or reads various data such as a program.

The unlocking/locking device 905 is a mechanism that is attached to thethumb turn of the door 8 and unlocks or locks the door 8 by rotating thethumb turn by being remotely controlled, or remotely operated. Theoperation device 907 is a part that is operated by a user. Examples ofthe operation device 907 includes a switch. The long-range communicationcircuit 909 is a communication circuit for performing data communicationwith the drive control server 7 via a communication network. The busline 910 is, for example, an address bus or a data bus, whichelectrically connects the components such as the CPU 901 illustrated inFIG. 4.

Functional Configuration:

A description is given below of an example of a functional configurationof each device included in the remote control system 1 with reference toFIG. 5 to FIG. 8. FIG. 5 is a block diagram illustrating a functionalconfiguration of the devices included in the remote control system 1according to the present embodiment.

Functional Configuration of PC:

As illustrated in FIG. 5, the PC 2 includes a datatransmission/reception unit 21, a reception unit 22, a display controlunit 24, and a storing/reading unit 29. These units are caused tofunction by operating one or more hardware components illustrated inFIG. 2 in cooperation with instructions of the CPU 201 according to thecontrol program for the PC loaded from the ROM 202 to the RAM 203.

The PC 2 further includes a storage unit 2000, which is implemented bythe ROM 202, the RAM 203, or the HD 204 illustrated in FIG. 2.

Functional Units of PC:

The data transmission/reception unit 21 of the PC 2, which isimplemented by the processing of the CPU 201 with respect to the networkI/F 209, transmits or receives various data (or information) to or fromother devices via the communication network 100.

The reception unit 22, which is implemented mainly by the processing ofthe CPU 201 with respect to the keyboard 211 or the mouse 212, receivesvarious selections or inputs from a use.

The display control unit 24 is implemented mainly by processing of theCPU 201 and displays various images on the display 208.

The storing/reading unit 29, which is mainly implemented by processingof the CPU 201, stores various data (or information) in the storage unit2000 or reads various data (or information) from the storage unit 2000.

Functional Configuration of Smartphone:

As illustrated in FIG. 5, the smartphone 3 includes a datatransmission/reception unit 31, a reception unit 32, an acquisition unit33, a display control unit 34, and a storing/reading unit 39. Theseunits are caused to function by operating one or more hardwarecomponents illustrated in FIG. 5 in cooperation with instructions of theCPU 301 according to the control program for the smartphone loaded fromthe EEPROM 304 to the RAM 303.

The smartphone 3 further includes a storage unit 3000, which isimplemented by the ROM 302, the RAM 303, or the EEPROM 304 illustratedin FIG. 3.

Functional Units of Smartphone:

The data transmission/reception unit 31 of the smartphone 3, which isimplemented mainly by the processing of the CPU 301 with respect to thelong-range communication circuit 312, transmits or receives various data(or information) to or from other devices via the communication network100.

The reception unit 32, which is mainly implemented by the processing ofthe CPU 301 with respect to the touch panel 321, receives variousselections or inputs from a user.

The acquisition unit 33, which is mainly implemented by the processingof the CPU 301 with respect to the imaging element I/F 314 andprocessing of the CPU 301, causes the CMOS 313 to capture an image of QRCODE, and acquires data embedded in QR CODE from the captured image.

The display control unit 34 is implemented mainly by processing of theCPU 301 and displays various images on the display 318.

The storing/reading unit 39, which is mainly implemented by processingof the CPU 301, stores various data (or information) in the storage unit3000 or reads various data (or information) from the storage unit 3000.

Functional Units of Reservation Management Server:

As illustrated in FIG. 5, the reservation management server 5 includes adata transmission/reception unit 51, and a storing/reading unit 59.These units are caused to function by operating one or more hardwarecomponents illustrated in FIG. 2 in cooperation with instructions of theCPU 501 according to the control program for the reservation managementserver loaded from the HD 504 to the RAM 503.

The reservation management server 5 further includes a storage unit5000, which is implemented by the ROM 502 or the HD 504 illustrated inFIG. 2.

Reservation Management Table:

FIG. 6 is a conceptual diagram illustrating a reservation managementtable according to the present embodiment. The reservation managementtable is a table for managing the schedules of users and resourcereservations including a reservation for a conference room. The storageunit 5000 stores a reservation management database (DB) 5001 includingthe reservation management table as illustrated in FIG. 6. Thereservation management table manages one or more records each includingdata items of reservation ID, reservation-making user account, eventname, resource ID, start date and time, end date and time, and expectedparticipant account, which are associated with each other.

The reservation ID is an example of reservation identificationinformation for identifying a specific reservation. Thereservation-making user account is an account of a reservation-makinguser who has reserved (has made a reservation for) a resource such asthe conference room for use. In a record of the reservation ID of“R001”, an email address of User A is indicated as the account of UserA. The reservation-making user account is an example ofreservation-making user identification information for identifying auser who made a reservation. The event name indicates a name of aconference that is held using the resources such as a conference room.The resource ID is an example of resource identification information foridentifying a resource such as a conference room. The start date andtime is a scheduled start date and time when the event is scheduled tostart. The end date and time is a scheduled end date and time when theevent is scheduled to end. The expected participant account is one ormore accounts of one or more users who is to participate in the event.In the description of the embodiment, an email address of acorresponding user is used as the expected participant account as is thecase with the reservation-making user account. The expected participantaccount is an example of expected participant identification informationfor identifying an expected participant.

The event name, the resource ID, the start date and time, and the enddate and time are included in reservation information.

Functional Units of Reservation Management Server:

The data transmission/reception unit 51 of the reservation managementserver 5, which is implemented by the processing of the CPU 501 withrespect to the network I/F 509, transmits or receives various data (orinformation) to or from other devices via the communication network 100.

The storing/reading unit 59, which is mainly implemented by processingof the CPU 501, stores various data (or information) in the storage unit5000 or reads various data (or information) from the storage unit 5000.

Functional Units of Intermediary Server:

As illustrated in FIG. 5, the intermediary server 6 includes a datatransmission/reception unit 61, an authentication unit 62, a generationunit 63, and a storing/reading unit 69. These units are caused tofunction by operating one or more hardware components illustrated inFIG. 2 in cooperation with instructions of the CPU 601 according to thecontrol program for the intermediary server loaded from the HD 604 tothe RAM 603.

The intermediary server 6 further includes a storage unit 6000, which isimplemented by the ROM 602 or the HD 604 illustrated in FIG. 2.

User Management Table:

FIG. 7A is a conceptual diagram illustrating a user management tableaccording to the present embodiment. The user management table is atable for managing individual information of each user. The storage unit6000 stores a user management DB 6001 including the user managementtable as illustrated in FIG. 7A. The user management table manages oneor more records each including data items of organization ID, useraccount, and user name, which are associated with each other.

The organization ID is an example of organization identificationinformation for identifying an organization (business operator, company)to which a corresponding user belongs. The user account is an example ofuser identification information for identifying a user. In the usermanagement table illustrated in FIG. 7A, an email address of acorresponding user is used as an account of the user. When the user isthe reservation-making user, the user account is managed as thereservation-making user account in the above-mentioned reservationinformation management table. When the user is one of the expectedparticipants, the user account is managed as the expected participantaccount in the above-mentioned reservation information management table.The user name is a name of a corresponding user.

Event Management Table:

FIG. 7B is a conceptual diagram illustrating an event management tableaccording to the present embodiment. The event management table is atable for managing detailed information of each event such as a meeting.The storage unit 6000 stores an event management DB 6002 including theevent management table as illustrated in FIG. 7B. The reservationmanagement table manages one or more records each including a data itemof event status in addition to the data items of reservation ID,reservation-making user account, event name, resource ID, start date andtime, end date and time, and expected participant account, which areassociated with each other. The redundant description of the sameinformation as the information managed in the reservation managementtable described above is omitted in the following. The event status isinformation that mainly indicates a status of an event such as aconference.

Key Type Management Table:

FIG. 7C is a conceptual diagram illustrating a key type management tableaccording to an embodiment of the present disclosure. The key typemanagement table is a table for managing a type of each key used forunlocking and locking a drive device such as a smart lock. The storageunit 6000 stores a key type management DB 6003 including the key typemanagement table illustrated in FIG. 7C. The key type management tablemanages one or more records each including data items of organizationID, resource name, resource ID, key type, drive device ID, and accesslocation information, which are associated with each other.

The organization ID and the resource ID are the same as the organizationID in the user information management table described above and theresource ID in the event management table described above, and thus theredundant description is omitted. The resource name is the name of aresource such as a conference room.

In addition, the key type indicates a type of method for unlocking andlocking (unlocking method). In the key type management table illustratedin FIG. 7C, “ELECTRONIC KEY”, “PHYSICAL KEY”, and “NONE” are indicatedas examples of key types. The key type of “ELECTRONIC KEY” indicates amethod of unlocking or locking a drive device such as the smart lock 9by using electronic information such as authentication information byremote control. The key type of “PHYSICAL KEY” indicates a method ofunlocking or locking in a way that a user inserts a physical key such asa key made of metal into a keyhole to unlock or lock without using adrive device such as the smart lock 9. The key type of “NONE” indicatesthat a key is not required to open (unlock) or close (lock) the door.

The drive device ID is an example of drive device identificationinformation for identifying a drive device such as the smart lock 9. Theaccess location information indicates an access destination whereinformation on the key is or indicates a location where the key actuallyis. The access location information indicates a location in relation tothe key. The location and the access location information differdepending on the key type.

When the key type is indicated as “ELECTRONIC KEY”, the accessdestination for the key indicates information on a location where theintermediary server 6 accesses via the communication network 100. In thekey type management table in FIG. 7C, a URL of the drive control server7 is indicated as the information on the location, which is the accessdestination.

When the key type is indicated as “PHYSICAL KEY”, the access locationinformation (destination) indicates a location where a user is to stopoff at (physically access). In the key type management table in FIG. 7C,1st floor security room where a corresponding physical key is stored andmanaged is indicated as information on the location (access locationinformation).

When the key type is indicated as “NONE”, there is no information on thelocation including the access destination, because the key is notrequired to open (unlock) or close (lock) the door.

Functional Units of Intermediary Server:

The data transmission/reception unit 61 of the intermediary server 6,which is implemented by the processing of the CPU 601 with respect tothe network I/F 609, transmits or receives various data (or information)to or from other devices via the communication network 100.

The authentication unit 62 is mainly implemented by processing of theCPU 601 and authenticates whether the reservation-making user has anauthority to reserve a resource such as a conference room.

The generation unit 63 is mainly implemented by processing of the CPU601 and generates a predetermined message using the information readfrom each of the user management DB 6001, the event management DB 6002,and the key type management DB 6003.

The storing/reading unit 69, which is mainly implemented by processingof the CPU 601, stores various data (or information) in the storage unit6000 or reads various data (or information) from the storage unit 6000.

Functional Configuration of Drive Control Server:

As illustrated in FIG. 5, the drive control server 7 includes a datatransmission/reception unit 71, an issuing unit 72, a determination unit75, and a storing/reading unit 79. These units are caused to function byoperating one or more hardware components illustrated in FIG. 2 incooperation with the instructions of the CPU 701 according to thecontrol program for the drive control server loaded from the HD 704 tothe RAM 703.

The drive control server 7 further includes a storage unit 7000, whichis implemented by the ROM 702 or the HD 704 illustrated in FIG. 2.

Drive Device Management Table:

FIG. 8 is a conceptual diagram illustrating a drive device managementtable according to an embodiment of the present disclosure. The drivedevice management table is a table for managing information on a drivedevice such as the smart lock 9. The storage unit 7000 stores a drivedevice management DB 7001 including the drive device management table asillustrated in FIG. 8. The drive device management table manages one ormore records each including data items of drive device ID, drive devicedestination information, authentication information, valid period of theauthentication information, and status of the drive device, which areassociated with each other.

The drive device ID is the same as the drive device ID managed in theabove-mentioned key type management table. The drive device ID allowsthe intermediary server 6 and the drive control server 7 to performprocessing in cooperation with each other.

The drive device destination information indicates a destination of acorresponding drive device such as the smart lock 9 on the communicationnetwork 100. The destination information is indicated by, for example,an internet protocol (IP) address or a media access control (MAC)address.

The authentication information is information required for anauthentication when a drive device such as the smart lock 9 unlocks orlocks. The authentication information is, for example, a passcode or apassword.

The valid period of the authentication information indicates a periodduring which the drive control server 7 can effectively use theauthentication information. As illustrated in FIG. 8, the same drivedevice (drive device ID “d001”) has two or more records each includesdifferent authentication information and the valid period of thecorresponding authentication information. Accordingly, even the resourceis the same conference room, the smart lock 9 is unlocked or locked onlyduring the period reserved by the corresponding reservation-making user.

The status of the drive device indicates a status of unlocking orlocking in relation to the drive device such as the smart lock 9.

Function Units of Drive Control Server:

The data transmission/reception unit 71 of the drive control server 7,which is implemented by the processing of the CPU 701 with respect tothe network I/F 709, transmits or receives various data (or information)to or from other devices via the communication network 100.

The issuing unit 72 is mainly implemented by processing of the CPU 701and issues the authentication information.

The determination unit 75 is mainly implemented by processing of the CPU701 and makes various determinations. For example, the determinationunit 75 determines validity of the authentication information.

The storing/reading unit 79, which is mainly implemented by processingof the CPU 701, stores various data (or information) in the storage unit7000 or reads various data (or information) from the storage unit 7000.

Functional configuration of Smart Lock:

As illustrated in FIG. 5, the smart lock 9 includes a datatransmission/reception unit 91 and a drive control unit 92. These unitsare caused to function by operating one or more hardware componentsillustrated in FIG. 4 in cooperation with instructions of the CPU 901according to the control program for the smart lock loaded from theNVRAM 904 to the RAM 903.

Functional Units of Smart Lock:

The data transmission/reception unit 91 of the smart lock 9, which isimplemented mainly by the processing of the CPU 901 with respect to thelong-range communication circuit 909, transmits or receives various data(or information) to or from other devices via the communication network100.

The drive control unit 92 is mainly implemented by processing of the CPU901 and drives the unlocking/locking device 905 to unlock or lock.

Processes or Operation:

A description is given below of processes or operation according to thepresent embodiment, with reference to FIG. 9 to FIG. 24.

Reservation Registration Process:

First, a case where User A reserves Conference Room A, which is anexample of the resource, in the reservation management server 5 by usingthe PC 2 is described with reference to FIG. 9 to FIG. 12. FIG. 9 is asequence diagram illustrating a reservation registration processaccording to an embodiment of the present disclosure. FIG. 10 is adiagram illustrating an example of a schedule input screen according toan embodiment of the present disclosure.

User A operates the PC 2 to input, with respect to a schedule inputscreen 1560 as illustrated in FIG. 10, the reservation information(event name, resource, event start time, event end time) and theexpected participants. Accordingly, the reception unit 22 receives theuser operations including the input or the selection in relation to thereservation information and the expected participants (S21). Theschedule input screen 1560 includes an input field 1561 for inputting anevent name, an input field 1562 for inputting a resource name, an inputfield 1563 for inputting a scheduled start date and time for the event,an input field 1564 for inputting a scheduled end date and time for theevent, a display area 1565 for displaying a name of a reservation-makinguser (account of the reservation-making user), and a selection field1566 for selecting the expected participants (accounts of the expectedparticipants) other than the reservation-making user. In the presentembodiment, the email addresses are used as the account of thereservation-making user and the accounts of the expected participants.

The data transmission/reception unit 21 of the PC 2 transmits, to thereservation management server 5, the information obtained by the useroperation of inputting or selecting in step S21 (reservation-making useraccount, expected participant accounts, reservation information) (S22).Then, the data transmission/reception unit 51 of the reservationmanagement server 5 receives the information. In addition, step S22 maybe executed after the reservation-making user (User A) obtains approvalto make the reservation from an approver such as a supervisor bysending, through the communication network 100, a request for theapproval and receiving the approval via a PC used by the supervisorthrough the communication network 100.

The storing/reading unit 59 of the reservation management server 5stores the information received in step S22 in the reservationmanagement DB 5001 after assigning a reservation ID to the informationto be managed in the reservation management DB 5001 (S23). After that,the data transmission/reception unit 51 transmits a completionnotification indicating that making the reservation has been completedto the PC 2 (S24). Then, the data transmission/reception unit 21 of thePC 2 receives the completion notification.

The data transmission/reception unit 51 of the reservation managementserver 5 further transmits, to the intermediary server, the information(reservation ID, reservation-making user account, expected participantaccounts, reservation information) stored in step S23 (S25). Then, thedata transmission/reception unit 61 of the intermediary server 6receives the information. Note that step S25 may be executed in aresponse to one of polling requests periodically transmitted from theintermediary server 6 to the reservation management server 5.

The intermediary server 6 performs user authentication based on adetermination whether the reservation-making user account received instep S25 is managed by the user management DB 6001 as a user account(S26).

In case that User is not Authenticated:

Next, a case where User A is not authenticated by the userauthentication in step S26 is described with reference to FIG. 11. FIG.11 is a sequence diagram illustrating a process performed in a case thatthe user is not authenticated as an authorized user, according to anembodiment of the present disclosure.

As illustrated in FIG. 11, the data transmission/reception unit 61 ofthe intermediary server 6 transmits a reservation cancellation requestto the reservation management server 5 (S31). The reservationcancellation request includes the reservation ID received in step S25.Then, the data transmission/reception unit 51 of the reservationmanagement server 5 receives the reservation cancellation request.

The storing/reading unit 59 of the reservation management server 5deletes the reservation ID and the information, which is stored togetherwith the reservation ID in step S23 (S32).

The generation unit 63 of the intermediary server 6 generates a messageto be transmitted to the PC 2, the message indicates that thereservation is not accepted, namely, making the reservation is failed(S33). Then, the data transmission/reception unit 61 transmits, to thePC 2, the message, which is generated in step S33 and indicates that thereservation is failed to be made (S34). In the present embodiment,because the data transmission/reception unit 61 of the intermediaryserver 6 has received an email address as the reservation-making useraccount in step S25, the data transmission/reception unit 61 transmitsthe message, which indicates that the reservation is failed to be made,by specifying the an email address as a transmission destination. Then,the data transmission/reception unit 21 of the PC 2 receives the messageindicating that the reservation is failed to be made. Then, the displaycontrol unit 24 of the PC 2 causes the display 208 to display themessage indicating that the reservation is failed to be made (S35).

In case that User is Authenticated:

Next, a case where User A is successfully authenticated by the userauthentication in step S26 is described with reference to FIG. 12. FIG.12 is a flowchart illustrating a key type determination processperformed by the intermediary server 6 when the user is authenticatedsuccessfully.

First, the storing/reading unit 69 associates the information items,reservation ID, reservation-making user account, expected participantsaccounts, and reservation information received in step S25, and storesthe associated information as a new record to be managed in the eventmanagement DB 6002 (S41). At this time, an “event status” in the newrecord is not managed.

Next, the storing/reading unit 69 reads corresponding key typeinformation by searching the key type management DB 6003 using theresource ID in the reservation information stored in step S41 as asearch key (S42). When the key type is indicated as “ELECTRONIC KEY”,the processing after step S61, which is described in detail later, isexecuted. When the key type is indicated as “PHYSICAL KEY”, theprocessing after step S81, which is be described in detail later, isexecuted. Further, when the key type is indicated as “NONE”, that is,when there is no key, the processing after step S101 is executed. Eachprocess corresponding to the key type is described below.

In Case of Electronic Key:

First, a case where the key type is indicated as “ELECTRONIC KEY” isdescribed with reference to FIG. 13 and FIG. 14. FIG. 13 is a sequencediagram illustrating a process of transmitting a message when the keytype is indicated as “ELECTRONIC KEY”, according to an embodiment of thepresent disclosure. FIG. 14 is an illustration of an example screendisplayed on a PC when the key type is indicated as “ELECTRONIC KEY,according to an embodiment of the present disclosure.

As illustrated in FIG. 13, the storing/reading unit 69 of theintermediary server 6 searches the key type management DB 6003 using theresource ID in the reservation information received in step S25 as asearch key to read a corresponding drive device ID and access locationinformation (S61). Then, the data transmission/reception unit 61transmits a request for authentication information to the accesslocation of the drive control server 7 (S62). The request includes thedrive device ID read in step S61. Then, the data transmission/receptionunit 71 of the drive control server 7 receives the request forauthentication information.

Next, the issuing unit 72 of the drive control server 7 issues uniqueauthentication information (S63). Then, the storing/reading unit 79stores the authentication information issued in step S63 as a data itemof the record in which the same drive device ID received in step S62 ismanaged, and the record including the authentication information ismanaged in the drive device management DB 7001. (S64).

Next, the data transmission/reception unit 71 transmits theauthentication information issued in step S63 to the intermediary server6 (S65). Then, the data transmission/reception unit 61 of theintermediary server 6 receives the authentication information.

Next, the storing/reading unit 69 of the intermediary server 6 searchesthe user management DB 6001 using the reservation-making user (User A)account received in step S25 as a search key to read the correspondinguser name (S66).

Next, the storing/reading unit 69 searches the key type management DB6003 using the resource ID in the reservation information received instep S41 as a search key to read the corresponding resource name (S67).

Next, the storing/reading unit 69 searches the event management DB 6002using the reservation-making user account received in step S41 as asearch key to read the corresponding reservation information (S68).Then, the generation unit 63 uses the authentication informationreceived in step S65 and the information read in steps S66 to S68(reservation name (user name of the reservation-making user), resourcename, reserved information) to generate a message that is a reservationcompletion message indicating that making the reservation is completedand to be transmitted together with the authentication information, asillustrated in FIG. 14 (S69).

Next, the data transmission/reception unit 61 of the intermediary server6 transmits to the PC 2 the reservation completion message, which isgenerated in step S69 and indicates that making the reservation iscompleted together with the authentication information (S70). Then, thedata transmission/reception unit 21 of the PC 2 receives the message.

The authentication information may always be the same informationcontent. In this case, the drive control server 7 does not execute theprocessing of step S63 but adjusts a time to transmit the authenticationinformation in step S70. For example, the intermediary server 6transmits the authentication information 10 minutes before theconference starts. Further, in step S70, the intermediary server 6 maytransmit a reservation completion message not only to the PC 2 used bythe reservation-making user (User A) but also to all or some of the PCseach of which is used by a corresponding participant who is scheduled toparticipate in the same conference.

Next, the storing/reading unit 69 manages the “event status” in therecord including the reservation-making user account read in step S68 as“authentication information has been informed” in the event managementDB 6002 (S71). As a result, the “event status”, which is not managed instep S41, is managed with new information.

Next, the display control unit 24 of the PC 2 causes the display 208 todisplay a message screen as illustrated in FIG. 14. This allows thereservation-making user (User A) who inputs or selects the reservationinformation in step S21 to obtain, in step S72, information indicatingthat making the reservation is completed in addition to theauthentication information required to unlock the resource.

In Case of Physical Key:

Next, a case where the key type is indicated as “PHYSICAL KEY” isdescribed with reference to FIG. 15 and FIG. 16. FIG. 15 is a sequencediagram illustrating a process of transmitting a message when the keytype is indicated as “PHYSICAL KEY”, according to an embodiment of thepresent disclosure. FIG. 16 is an illustration of an example screendisplayed on a PC when the key type is indicated as “PHYSICAL KEY”,according to an embodiment of the present disclosure.

As illustrated in FIG. 15, the storing/reading unit 69 of theintermediary server 6 searches the key type management DB 6003 using theresource ID in the reservation information received in step S25 as asearch key to read a corresponding drive device ID and access locationinformation (S81). Unlike the case of “ELECTRONIC KEY” described above,there is no processing (steps S62 to S65) for acquiring theauthentication information from the drive control server 7. Thestoring/reading unit 69 of the intermediary server 6 searches the usermanagement DB 6001 using the reservation-making user (User A) accountreceived in step S25 as a search key to read the corresponding user name(S82).

Next, the storing/reading unit 69 searches the key type management DB6003 using the resource ID in the reservation information received instep S41 as a search key to read the corresponding resource name (S83).

Next, the storing/reading unit 69 searches the event management DB 6002using the reservation-making user account received in step S41 as asearch key to read the corresponding reservation information (S84).Then, the generation unit 63 uses the information (access locationinformation, reservation name (user name of the reservation-makinguser), resource name, reservation information) read in steps S 81 to S84to generate a message that is a reservation completion messageindicating that making the reservation is completed and to betransmitted together with the access location information, asillustrated in FIG. 16 (S85). Since the key type is indicated as“PHYSICAL KEY”, a location where a corresponding physical key is stored,managed, or kept, (for example, security room on 1st floor) is indicatedas the access location information, as illustrated in FIG. 16.

Next, the data transmission/reception unit 61 of the intermediary server6 transmits to the PC 2 the message, which is generated in step S85 andindicates that making the reservation is completed together with theaccess location information (S86). Then, the data transmission/receptionunit 21 of the PC 2 receives the message. Then, the storing/reading unit69 manages the “event status” in the record including thereservation-making user account read in step S84 as “access locationinformation has been informed” in the event management DB 6002 (S87). Asa result, the “event status”, which is not managed in step S41, ismanaged with new information.

Next, the display control unit 24 of the PC 2 causes the display 208 todisplay a message screen as illustrated in FIG. 16 (S88). This allowsthe reservation-making user (User A) who inputs or selects thereservation information in step S21 to obtain, in step S88, informationindicating that making the reservation is completed in addition to theaccess location information required to unlock the resource.

In Case that Kye is Not Used:

Subsequently, a case where the key type is indicated as “NONE” isdescribed with reference to FIG. 17 and FIG. 18. FIG. 17 is a sequencediagram illustrating a process of transmitting a message when the keytype is indicated as “NONE”, according to an embodiment of the presentdisclosure. FIG. 18 is an illustration of an example screen displayed ona PC when the key type is indicated as “NONE”, according to anembodiment of the present disclosure. The key type, “NONE”, means thereis no key to be used. Accordingly, the storing/reading unit 69 is notrequired to read the access location information as in step S61 (S81).

As illustrated in FIG. 17, the storing/reading unit 69 of theintermediary server 6 searches the user management DB 6001 using thereservation-making user (User A) account received in step S25 as asearch key to read the corresponding user name (S101).

Next, the storing/reading unit 69 searches the key type management DB6003 using the resource ID in the reservation information received instep S41 as a search key to read the corresponding resource name (S102).

Next, the storing/reading unit 69 searches the event management DB 6002using the reservation-making user account received in step S41 as asearch key to read the corresponding reservation information (S103).Then, the generation unit 63 uses the information (reservation name(user name of the reservation-making user), resource name, reservationinformation) read in steps S101 to S103 to generate a message indicatingthat making the reservation is completed as illustrated in FIG. 18(S104).

Next, the data transmission/reception unit 61 of the intermediary server6 transmits to the PC 2 the message, which is generated in step S85 andindicates that making the reservation is completed (S105). Then, thedata transmission/reception unit 21 of the PC 2 receives a message fornotifying the completion of the reservation. Then, the storing/readingunit 69 manages the “event status” in the record including thereservation-making user account read in step S103 as “reservationcompletion has been informed” in the event management DB 6002 (S106). Asa result, the “event status”, which is not managed in step

S41, is managed with new information.

Next, the display control unit 24 of the PC 2 causes the display 208 todisplay a message screen as illustrated in FIG. 16. This allows thereservation-making user (User A) who inputs or selects the reservationinformation in step S21 to obtain, in step S107, information indicatingthat making the reservation is completed.

Remote Unlocking Process Using Electronic Key:

A description is given below of a remote unlocking process using a keyof which the key type is indicated as “ELECTRONIC KEY” with respect tothe smart lock 9 with reference to FIG. 19 to FIG. 22 (FIG. 22A to FIG.22D). FIG. 19 to FIG. 21 are sequence diagrams illustrating a remoteunlocking process when the key type is indicated as “ELECTRONIC KEY”,according to an embodiment of the present disclosure. FIG. 22A to FIG.22D are illustrations of example screens displayed on a smartphone whena conference starts, according to an embodiment of the presentdisclosure. In the description of the embodiment, User A who is in thefront of the door 8 and the outside of Conference Room A unlocks thesmart lock using his or her smartphone 3.

First, the acquisition unit 33 of the smartphone 3 obtains a resource IDand access destination information such as a URL, which are embedded inQR CODE indicated with the door 8 as illustrated in FIG. 1, by capturingan image of QR CODE according to a user operation performed by User A(S121). Further, the storing/reading unit 39 reads thereservation-making user account as User A stored in the storage unit3000 (S122). Then, the data transmission/reception unit 31 of thesmartphone 3 transmits a request for reservation information to theintermediary server 6 indicated by the access destination information(S123). The request for the reservation information includes theresource ID acquired in step S121 and the reservation-making user (UserA) account read in step S122. Then, the data transmission/reception unit61 of the intermediary server 6 receives the request for reservationinformation (S123).

Next, the storing/reading unit 69 of the intermediary server 6 searchesthe key type management DB 6003 using the resource ID in the reservationinformation received in step S123 as a search key to read thecorresponding resource name (S124).

Next, the storing/reading unit 69 of the intermediary server 6 searchesthe event management DB 6002 using the reservation-making user accountreceived in step S123 as a search key to read all reservation IDs andreservation information corresponding to all the reservation IDs on theevent execution date (S125).

Next, the storing/reading unit 69 of the intermediary server 6 searchesthe user management DB 6001 using the reservation-making user (User A)account received in step S123 as a search key to read the correspondinguser name (S126). Then, the generation unit 63 uses the information(resource name, reservation information for all the reservations on theexecution date, reservation name (user name of the reservation-makinguser)) read in steps S124 to S126 to generate a reservation contentmessage indicating details of the reservation and prompting thereservation-making user for performing a process to start the event, asillustrated in FIG. 22A (S127).

Next, the data transmission/reception unit 61 of the intermediary server6 transmits the reservation content message generated in step S127 tothe smartphone 3 (S128). The reservation content message includes thereservation ID. Then, the data transmission/reception unit 31 of thesmartphone 3 receives the message.

Next, the display control unit 34 of the smartphone 3 causes the display318 to display a message screen as illustrated in FIG. 22A (S129). Themessage screen includes a display field 401 for displaying a resourcename (Conference Room A), a display field 402 for displaying an eventname (Regular Meeting), a display field 403 for displaying a start dateand time and end date and time, a display field 404 for displaying aname of a reservation-making user (User A), and a display field 407 fordisplaying a start date and time and an end date and time for each ofthe other events on the same day. The message screen further includes, a“Start” button 411 and a “Cancel” button 412. The “Start” button 411 isa button to be pressed by, for example, a reservation-making user whenthe smart lock 9 is remotely controlled and unlocked and an event isstarted. The “Cancel” button 412 is a button to be pressed by, forexample, a reservation-making user when the smart lock 9 is remotelycontrolled and unlocked and an event is canceled without starting. Asthe “Start” button, an “Unlock” button may be used.

When the reservation-making user (User A) presses the “Start” button411, the reception unit 32 receives the user operation for remotelycontrolling the smart lock 9 to be unlocked and starting the event(S130). As a result, the display control unit 34 pops up anauthentication information input screen 450 for inputting theauthentication information as illustrated in FIG. 22B (S131). Asillustrated in FIG. 22B, the authentication information input screen 450includes an authentication information input field 451 for inputtingauthentication information (authentication code), an “OK” button 452,and a “Cancel” button 453. The “OK” button 452 is a button to be pressedwhen the reservation-making user (User A) confirms the authenticationinformation (code) entered in the authentication information input field451. The “Cancel” button 453 is a button to be pressed when thereservation-making user (User A) confirms the authentication information(code) entered in the authentication information input field 451.

When the reservation-making user (User A) inputs the authenticationinformation obtained in step S72 in the authentication information inputfield 451 and presses the “OK” button 452, the reception unit 32receives the input of the authentication information (S132).

Subsequently, after the processing of step S132, the datatransmission/reception unit 31 transmits an unlock request for the smartlock 9 and an event start request to the intermediary server 6, asillustrated in FIG. 20 (S141). The unlock request and the start requestinclude the reservation ID received in step S128 and the authenticationinformation received in step S132. Then, the data transmission/receptionunit 61 of the intermediary server 6 receives the unlock request and thestart request.

Next, the storing/reading unit 69 of the intermediary server 6 searchesthe event management DB 6002 using the reservation ID received in stepS141 as a search key to read the corresponding resource ID (S142).

Next, the storing/reading unit 69 searches the key type management DB6003 using the resource ID read in step S142 as a search key to read thecorresponding drive device ID and access location information (S143).Then, the data transmission/reception unit 61 transmits a remote controlstart request for the smart lock 9 to the drive control server 7indicated by the access location information (S144). This requestincludes the drive device ID read in step S143 and the authenticationinformation received in step S141. Then, the data transmission/receptionunit 71 of the drive control server 7 receives the remote control startrequest.

Next, the storing/reading unit 79 of the drive control server 7 searchesthe drive device management DB 7001 using the drive device ID receivedin step S144 as a search key to read information on a valid period ofthe corresponding authentication information (S145).

Next, the determination unit 75 determines the validity of theauthentication information received in step S144. More specifically, thedetermination unit 75 determines whether a current date and time iswithin the valid period of the authentication information read in stepS145 (S146). In the following, a case where the determination unit 75determines that the authentication information is valid because thecurrent date and time is within the valid period is described.

Next, the storing/reading unit 79 searches the drive device managementDB 7001 using the driving device ID received in step S144 as a searchkey to read the corresponding drive device destination information (forexample, IP address) (S147). Then, the data transmission/reception unit71 transmits an unlock request to the smart lock 9 indicated by thedrive device destination information read in step S147 (S148). Then, thedata transmission/reception unit 91 of the smart lock 9 receives theunlock request.

Next, the drive control unit 92 of the smart lock 9 drives theunlocking/locking device 905 to unlock (S149). As a result, thesmartphone 3 remotely unlocks the smart lock 9 via the intermediaryserver 6 and the drive control server 7.

Subsequently, as illustrated in FIG. 21, the data transmission/receptionunit 91 of the smart lock 9 transmits a response indicating thatunlocking is completed to the drive control server 7 (S161). Then, thedata transmission/reception unit 71 of the drive control server 7receives the response.

Next, the storing/reading unit 79 of the drive control server 7 changes“status of drive device” in the record including the drive device IDreceived in step S144 from “locked” to “unlocked”. (S162). Then, thedata transmission/reception unit 71 of the drive control server 7transmits a response indicating that unlocking is completed to theintermediary server 6 (S163). Then, the data transmission/reception unit81 of the intermediary server 6 receives the response.

Next, the storing/reading unit 69 of the intermediary server 6 changes“event status” in the record including the reservation ID received instep S141 from “authentication information has been informed” to “eventhas started”. (S164). Then, the data transmission/reception unit 61 ofthe intermediary server 6 transmits a response indicating that unlockingis completed to the smartphone 3 (S165). Then, the datatransmission/reception unit 31 of the smartphone 3 receives theresponse.

Next, the display control unit 34 of the smartphone 3 displays an “End”button 413 as illustrated in FIG. 22C (S166). This “End” button 413 is abutton to be pressed by a reservation-making user (User A) or the likewhen the event is ended. In addition to sound indicating unlocking ofthe smart lock 9, the “End” button 413 being displayed allows thereservation-making user (User A) to know unlocking is completed.

In a case that the reservation-making user (User A) mistakenly inputsthe authentication information on the screen illustrated in FIG. 22B,the display control unit 34 displays an authentication information inputscreen 460 as a pop-up screen again as illustrated in FIG. 22D. Asillustrated in FIG. 22D, the authentication information input screen 460includes an authentication information input field 461 for inputtingauthentication information (authentication code), an “OK” button 462,and a “Cancel” button 463. The “OK” button 462 is a button to be pressedwhen the reservation-making user (User A) confirms the authenticationinformation (code) entered in the authentication information input field461. The “Cancel” button 463 is a button to be pressed when thereservation-making user (User A) confirms the authentication information(code) entered in the authentication information input field 461. Whenthe reservation-making user (User A) inputs the authenticationinformation obtained in step S72 in the authentication information inputfield 461 and presses the “OK” button 462, the reception unit 32receives the input of the authentication information (S132).

Remote Locking Process in Case of Electronic Key:

A description is given below of a remote locking process with“ELECTRONIC KEY” with respect to the smart lock 9 with reference to FIG.23 to FIG. 24. FIG. 23 and FIG. 24 are sequence diagrams illustrating aremote locking process when the key type is indicated as “ELECTRONICKEY”, according to an embodiment of the present disclosure.

First, after the event ends, the reservation-making user and all theparticipants leave Conference Room A, and when the reservation-makinguser (User A) presses the “End” button 413 illustrated in FIG. 22C, thereception unit 32 receives the locking of the drive device and the endof the event (S181).

Next, the data transmission/reception unit 31 transmits a lock requestfor the smart lock 9 and an event end request to the intermediary server6, as illustrated in FIG. 23 (S182). The lock request and the endrequest include the reservation ID received in step S182. Then, the datatransmission/reception unit 61 of the intermediary server 6 receives thelock request and the end request.

Next, the storing/reading unit 69 of the intermediary server 6 searchesthe event management DB 6002 using the reservation ID received in stepS182 as a search key to read the corresponding resource ID (S183).

Next, the storing/reading unit 69 searches the key type management DB6003 using the resource ID read in step S183 as a search key to read thecorresponding drive device ID and access location information (S184).Then, the data transmission/reception unit 61 transmits a remote controlstart request for the smart lock 9 to the drive control server 7indicated by the access location information (S185). The requestincludes the drive device ID read in step S184. Then, the datatransmission/reception unit 71 of the drive control server 7 receivesthe remote control start request.

Next, the storing/reading unit 79 of the drive control server 7 searchesthe drive device management DB 7001 using the driving device ID receivedin step S185 as a search key to read the corresponding drive devicedestination information (for example, IP address) (S186). Then, the datatransmission/reception unit 71 transmits a lock request to the smartlock 9 indicated by the drive device destination information read instep S186 (S187). Then, the data transmission/reception unit 91 of thesmart lock 9 receives the lock request.

Next, the drive control unit 92 of the smart lock 9 drives theunlocking/locking device 905 to lock (S188). As a result, the smartphone3 remotely locks the smart lock 9 via the intermediary server 6 and thedrive control server 7.

Subsequently, as illustrated in FIG. 24, the data transmission/receptionunit 91 of the smart lock 9 transmits a response indicating that lockingis completed to the drive control server 7 (S201). Then, the datatransmission/reception unit 71 of the drive control server 7 receivesthe response.

Next, the storing/reading unit 79 of the drive control server 7 changes“status of drive device” in the record including the drive device IDreceived in step S185 from “unlocked” to “locked”. (S202). Then, thedata transmission/reception unit 71 of the drive control server 7transmits a response indicating that locking is completed to theintermediary server 6 (S203). Then, the data transmission/reception unit81 of the intermediary server 6 receives the response.

Next, the storing/reading unit 69 of the intermediary server 6 changes“event status” in the record including the reservation ID received instep S182 from “event has started” to “event ends”. (S204). Then, thedata transmission/reception unit 61 of the intermediary server 6transmits a response indicating that locking is completed to thesmartphone 3 (S205). Then, the data transmission/reception unit 31 ofthe smartphone 3 receives the response.

Next, the display control unit 34 of the smartphone 3 causes the display318 to display a message indicating that locking is completed. Thedisplay control unit 34 of the smartphone 3 causes the display 318 todisplay the “End” button 413. In addition to sound indicating locking ofthe smart lock 9, the “End” button 413 being displayed allows thereservation-making user (User A) to know locking is completed.

As described above, according to the present embodiment, theintermediary server 6 mediates between a reservation management server5, which manages the resource reservations received from the PC 2 usedto registers a reservation, and the drive control server 7, whichremotely controls the smart lock 9 for unlocking the resource.Accordingly, the intermediary server 6 provides the PC 2 with theauthentication information required for unlocking the smart lock 9 usedfor unlocking the reserved resource. This reduces complicated processesfor the reservation-making user (user).

QR CODE is an example of an information representing item. In additionto QR CODE, examples of the information representing thing item includean Integrated Circuit (IC) tag and a beacon transmitter.

When the information representing item is an IC tag, the acquisitionunit 33 of the smartphone 3 is implemented by the processing of the CPU301 with respect to the short-range communication circuit 320, but notby the processing of the CPU 301 with respect to the imaging element I/F314. A resource ID and access destination information are acquired byshort-range communication technology such as Near Field Communication(NFC) (registered trademark) and Bluetooth (registered trademark) (seeS121). Since the IC tag is attached to a structure such as the door 8,the IC tag and the resource are associated with each other.

In addition, when the information representing item is a beacontransmitter, the acquisition unit 33 of the smartphone 3 is implementedby the processing of the CPU 301 with respect to the short-rangecommunication circuit 320, but not by the processing of the CPU 301 withrespect to the imaging element I/F 314. When entering a radio wave areaof the beacon transmitter, the smartphone 3 acquires a resource ID andaccess destination information by the radio wave transmitted from thebeacon transmitter (see S121). Since the beacon transmitter is attachedto a structure such as the door 8, the beacon transmitter and theresource are associated with each other.

In the above description of the embodiment, the example cases in each ofwhich a QR CODE sticker, an IC tag, or a beacon transmitter is attachedto the door 8 of a conference room are given, but the present disclosureis not limited to this. For example, instead of the door 8, a structuresuch as a wall portion other than the door of the conference room inwhich the door 8 is installed may be used to be attached.

Further, in the above description of the embodiment, a conference roomwhich is a shared resource is used as an example of a resource, but thepresent disclosure is not limited to this. For example, as anotherexample of the resource, a shared mobile body such as an aircraft, avehicle, or a ship may be used. Further, the smart lock 9 may not beattached to the outer surface of the door and may be a part of themechanism inside the door. For example, a mechanism of the smart lock 9may be set in a door of a vehicle to be used for a car sharing service.

Further, in the above description of the embodiment, the case where theremote control system remotely controls unlocking and locking, but thepresent disclosure is not limited this. For example, at least one ofunlocking and locking may be remotely controlled.

Each of the above-described hardware components including the CPU 201,the CPU 301, the CPU 501, the CPU 601, and the CPU 701 may be a singleunit or a plurality of units.

Each of the functions of the described embodiments may be implemented byone or more processing circuits or circuitry. Here, the “processingcircuit” in the present embodiment includes a processor programmed toexecute each function by software, such as a processor implemented by anelectronic circuit, and devices such as an application specificintegrated circuit (ASIC), a digital signal processor (DSP), a fieldprogrammable gate array (FPGA), a system on a chip (SOC), a graphicsprocessing unit (GPU), and a conventional circuit module designed toexecute each function described above.

The above-described embodiments are illustrative and do not limit thepresent invention. Thus, numerous additional modifications andvariations are possible in light of the above teachings. For example,elements and/or features of different illustrative embodiments may becombined with each other and/or substituted for each other within thescope of the present invention. Any one of the above-describedoperations may be performed in various other ways, for example, in anorder different from the one described above.

In a conventional technology, when a resource is a shared property,which is shared resource, shared by a plurality of users, a resourcereservation is often registered and managed in advance in a reservationmanagement service (system) in order to make effective use of the sharedresource. However, this does not mean that a smart lock of the resourceis remotely controlled by the reservation management service. In a casethat a user is required to unlock or lock a smart lock of the reservedresource for using the reserved resource by using electronicinformation, the user is required to obtain the electronic information,such as a passcode used to unlock the reserved resource, from anothersystem that remotely control the smart lock while making a reservationfor the resource with the reservation management service. That is, insuch a conventional technology, the user is required to performcomplicated processes.

According to the above-described embodiment of the disclosure, theintermediary server mediates the reservation management server, whichmanages a reservation for a resource received from the registrationterminal that registers the reservation, and the drive control server,which remotely controls the drive device for unlocking the resource. Dueto this, the intermediary server is able to provide the registrationterminal with authentication information required to cause the drivedevice to unlock the reserved resource. This reduces complicatedprocesses for the reservation-making user (user).

1. An intermediary server, comprising circuitry configured to receive,from a reservation management server, resource identificationinformation for identifying a resource, the reservation managementserver managing a reservation for the resource and receiving thereservation from a registration terminal that registers the reservation,transmit, to a drive control server, drive device identificationinformation for identifying a drive device corresponding to the resourceidentification information, the drive control server remotelycontrolling the drive device used to unlock the resource, receive, fromthe drive control server, authentication information to be used tounlock the resource with the drive device identified by the drive deviceidentification information, and transmit, to the registration terminal,the authentication information.
 2. The intermediary server of claim 1,wherein the circuitry further determines whether to transmit the drivedevice identification information to the drive control server dependingon an unlocking method associated with the resource identificationinformation.
 3. The intermediary server of claim 2, wherein theunlocking method includes a plurality of unlocking methods including afirst method that uses an electronic key and a second method that uses aphysical key, the first method remotely controlling the drive device tounlock the resource using the electronic key, and wherein, in case thatthe unlocking method corresponding to the resource identificationinformation is the first method, the circuitry transmits the drivedevice identification to the drive control server.
 4. The intermediaryserver of claim 3, wherein the received resource identificationinformation has been acquired, using a communication terminal, based oninformation representing item associated with the resource, and whereinthe circuitry transmits, to the communication terminal a resource namecorresponding to the resource identification information.
 5. Theintermediary server of claim 4, wherein the circuitry receives, from thecommunication terminal, user identification information for identifyinga user of the communication terminal, and transmits, to thecommunication terminal, information on a scheduled start time and endtime for usage of the resource reserved by the user identified by theuser identification information.
 6. The intermediary server of claim 5,wherein the circuitry receives, from the communication terminal, theauthentication information and reservation identification informationfor identifying the reservation, and transmits, to the drive controlserver, the authentication information and the drive deviceidentification information corresponding to the reservationidentification information.
 7. The intermediary server of claim 6,wherein the circuitry receives, from the drive control server anunlocking completion notification, the unlocking completion notificationbeing transmitted after the drive control server remotely controls thedrive device for unlocking the resource and the unlocking of theresource is completed, and transmits, to the communication terminal,information indicating the unlocking completion notification.
 8. Aremote control system, comprising: a drive device that is remotelycontrolled by a drive control server and used to unlock a resource; andan intermediary server, the drive device including drive devicecircuitry being configured to unlock the resource based onauthentication information, in response to a request to unlock theresource, the request being transmitted from the drive control server,the intermediary server including intermediary server circuitry beingconfigured to receive, from a reservation management server, resourceidentification information for identifying the resource, the reservationmanagement server managing a reservation for the resource and receivingthe reservation from a registration terminal that registers thereservation, transmit, to the drive control server, drive deviceidentification information for identifying the drive devicecorresponding to the resource identification information, the drivecontrol server remotely controlling the drive device used to unlock theresource, receive, from the drive control server, authenticationinformation to be used to unlock the resource with the drive deviceidentified by the drive device identification information, and transmit,to the registration terminal, the authentication information.
 9. Amediating method, comprising: receiving, from a reservation managementserver, resource identification information for identifying a resource,the reservation management server managing a reservation for theresource and receiving the reservation from a registration terminal thatregisters the reservation; transmitting, to a drive control server,drive device identification information for identifying a drive devicecorresponding to the resource identification information, the drivecontrol server remotely controlling the drive device used to unlock theresource; receiving, from the drive control server, authenticationinformation to be used to unlock the resource with the drive deviceidentified by the drive device identification information; andtransmitting, to the registration terminal, the authenticationinformation.